TattleTale provides very complete information about your computer and its system related software. The information can be viewed on screen by category, printed, written to a standard text file, or output in database readable format. As such, it also provides a record of your system configuration that can be used for reporting problems to software and hardware manufacturers, to compare configurations across multiple computers, or to simply learn about your machine. Information categories covered are: the CPU, Volumes + Drives, Monitors, Nubus Devices, SCSI Devices, ADB Devices, Serial Ports, General System Attributes, Startup Environment, System Files (System, Finder, INITS, CDEVs, RDEVs etc.), DAs, Fonts, Drivers, Open Files, Processes, and Available/UnAvailable Traps. In addition, it enables you to Mount Volumes and Close Files that were left open. The information provided varies greatly among these categories and is best understood simply by going to the dialog window and browsing through the above categories.
NOTE: The Traps information is valuable for programmers who are always wondering if a particular combination of system software and hardware implements a certain trap.
• SYSTEM REQUIREMENTS:
TattleTale is compatible with the Mac+ and newer machines and requires System 4.2 or higher. It is also compatible with System 7 and takes advantage of some of its enhanced system information features as well as balloon help. Note that there is a marked difference between the information available under system 4.2 compared to the 6.X systems and higher.
TattleTale 1.3 is available in two versions. This document describes the Application version. Under most circumstances, the DA version operates without problems. However, under System 7 there is considerably less memory allocated to DAs than under earlier systems. This and other particulars in your system can cause TattleTale DA to fail under memory intensive operations such as printing. This Application version of TattleTale was created for those people who experience problems with the DA version.
TattleTale.Traps expects to be found in the System Folder, but you can rename it or put it anywhere you want. However, you must describe this change for TattleTale as described under Trap Related Features below.
• GENERAL OPERATION:
TattleTale consists primarily of a menu and a modeless dialog window. When you initially run it, the dialog window is visible and the first category of information is already displayed in a scrolling list. Subsequent categories are selected from the Pop-up Menu above the list. Categories which are not available for a given computer and system software combination (e.g. Nubus on a Mac+ or Processes under Uni-Finder in System 6.X or lower) are dimmed and cannot be selected. The Close button and the Close Box both close the window but leave TattleTale active. Get System Info in the TattleTale Menu will re-open the window. You can Quit completely from the File Menu.
Printing is also controlled from the TattleTale Menu. From here you access Page Setup and two printing choices. You may print the list which is currently displayed (Print Current) or you may select Reports, which prints the reports which you select.
Reports also provides the capability of writing the reports to a standard text file or a tab-delimited Text File. Selecting "Write Std Reports to Text File" simply streams the reports that you choose in screen format to one standard text file for subsequent editing.
Similar to this is the "Write Bug Report to Text File" option. Associated with this option is the "Primary Bug Reports" button which chooses the standard reports that would be helpful to the person to whom you are reporting a bug. Another button, "Bug Explanation..." accesses a dialog which allows you to describe the problem with the program and also allows you to save and load the specific text. A third related button, "Bug Reported By", allows you to specify standard information related to the reporting individual. The reporter information is permanent across invocations to TattleTale.
"Write to Tab-Delimited Text File" is used for creating a database readable file. The default format is a Field Name line followed by a line of associated Data, all separated by tabs and ending in a carriage return. All lines are preceded by two additional columns: 1) the name of the report the data came from, and 2) the Chooser name of the reporting computer. In the case of reports which include multiple items which are the same (e.g. Drives, Fonts, DAs, etc.), there is a Header line and a Data line for each member of the group. Where there is preliminary information for a group (e.g. in the Serial Ports report), the name of the preliminary report has a "-H" appended to it so that you know what set of fields will be following. You may eliminate Field Name lines completely by checking the "Data Only" box and you may eliminate data interpretations (items enclosed in parentheses) by checking "Remove (Data Interpretations)". Also note that the Screen, Printed, and normal Text File reports include only those items of data which are appropriate in a given situation as opposed to the tab-delimited Text File reports which include all possible fields for consistency in reading the data into a database. It is suggested that you experiment with the generated tab-delimited Text File before designing any reports which might use this data.
Help, consisting of this text, is available either from the dialog window or the Apple menu. At times you will want to refresh the information in your window. Obvious refreshes happen automatically, but you can do it manually simply by re-selecting the menu item from the Pop-up Menu.
• TRAP RELATED FEATURES:
TattleTale provides information regarding Traps in two different formats. UnAvailable Traps lists those "official" Apple traps that are not available on your particular combination of computer and system software according to A-Trap Number and Name. Available Traps lists all those A-Traps which, through testing each trap, are shown to be "active" - that is, they do not have the _Unimplemented Trap address assigned to them. As can be seen from this list, there are many more implemented traps than documented traps. The primary reason for this is that many of them are used by internal routines which Apple reserves the right to change in the future.
To allow for changes in the Trap list over time, Commands to manipulate this file are located under the Main Menu . If this list is not kept up to date, the UnAvailable Traps list will not reflect new traps that are not available and the Available Traps List will show the A-Traps Number for available traps but will be missing any new Trap Names.
The "official" traps are included with TattleTale as TattleTale.Traps. If you simply wish to change the name or location of TattleTale.Traps, rename it and/or put it where you want, and then select Change Database File and you will be prompted to find the file. The new name and/or location will be used until you decide to change it.
In regard to changing the contents of the file, they are originally derived from MPW's Traps.p file which TattleTale converts into it's own database format. If you want to see the format of the original file, Database to Text File will prompt you to convert the database file to a text file which you can then view and/or modify on any text editor. If you wish to merge a modified traps text file with the database, select Merge Text File. This will incorporate any additions included in the file and ignore any duplications. If you have direct access to an up-to-date traps list, you can use New Database File to completely regenerate the database.
• Change History:
1.3
• First Application version.
• Fixed problem with Help Balloons flashing when the cursor was in a non-TattleTale item.
• Added item to Driver list to reflect not only the original status of flags but the status as of the time that the report is generated. (Idea courtesy of Miles Waldron)
• Changed the Serial Port report to better reflect situations when AppleTalk is connected. (Suggestion courtesy of Don Paul)
• Improved ability to more accurately reflect the status of the Nubus/PDS Slots.
• Changed method and report format for identifying devices connected to the ADB port.
• Fixed bug in the SCSI report which sometimes duplicated device information from one device to the next. The SCSI report also now reports the SCSI #0 drive as internal. (Bugs reported by Don Paul)
• Updated the Traps file to reflect traps missing from MPW's Traps.p file. (Information courtesy of Allan Muluf)
• Updated information to correctly identify PowerBooks, Quadras, and Mac Classic II.
• Fixed bug in Font report by gathered both BitMap and TrueType fonts into a combined family and altered the format to accomodate this change.
1.3.1
• Fixed problem with menus not appearing under certain situations. (Bug reported by Bob Seaver)
• Minor bug fixes
Remaining Requests
• Remove “◊” markers as they are distracting. The listing started out without the markers and was confusing without them. I guess you’ll have to trust me on this one. All markers, however, have been removed from any data written to a text file.
• Remove form feeds when multiple reports are printed as it wastes paper. This has been addressed by allowing any selected reports to be streamed to one text file for editing and continuous printing.
Miscellaneous
• I have had one report that the “Max Open Files” information under the System Startup listing is incorrect. Actually, all values in this listing are read directly from the Boot Blocks on your boot drive and are meant to reflect what is recorded there. This is the information used to configure your machine on startup, and in most cases will not change during the current startup of your machine. There are, however, some INITs like “Up Your FCB’s” which dynamically change the number of file control blocks as you use your machine. If you want a current reading of the maximum files currently allocated you must refer to the CDEV controlling that INIT.
• NOTICE:
This software is ECO-Ware. If you use it, please go a little further out of your way to do something environmentally sensitive the next chance you get. The program and the TattleTale name are copyrighted, credits and all documentation must be retained, but the program may be freely distributed at no charge to the user except media costs or normal downloading charges. If any user modifications are made to TattleTale, the resulting program may not be distributed in any manner whatsoever. TattleTale is distributed with no warranties, implied or expressed.
• A special thanks to Dick Hodges for his help in the original beta testing.
Please send questions, comments, suggestions, problems, etc. to:
